Framework, architecture, method and system for reducing latency of business operations of an enterprise

ABSTRACT

A framework, architecture, system and method are provided for reducing business transaction latencies thereby enabling an enterprise to run as a zero latency enterprise (ZLE). The present invention enables the enterprise to integrate its services, applications and data in real time. An enterprise running as a ZLE has a uniform global view of its past and current business transactions, including its customer interactions, internal business operations, supply chain management and more; and this uniform global view can be obtained from anywhere across the enterprise and be used for real-time decision making. Namely, an enterprise equipped to run as a ZLE is capable of integrating, in real time, its enterprise-wide data, applications, business transactions, operations and values. Consequently, an enterprise conducting its business as a ZLE exhibits superior management of its resources, operations and customer care.

REFERENCE TO PRIOR APPLICATION

[0001] This application claims the benefit of and incorporates byreference U.S. Provisional Application No. 60/266,003 filed Feb. 2,2001.

CROSS REFERENCE TO RELATED APPLICATION

[0002] This application is related to and incorporates by reference U.S.patent application Ser. No. ______ filed ______ entitled “Enabling aZero Latency Enterprise,” and Ser. No. ______ filed ______ entitled“Zero Latency Enriched Publish and Subscribe.”

BACKGROUND OF THE INVENTION

[0003] 1. Field of the Invention

[0004] This application relates to an information technology (IT)infrastructure of an enterprise, and specifically, an IT infrastructurethat enables a zero latency enterprise (ZLE). The present inventionenables the enterprise to integrate its services, applications and datain real time, hence the ZLE.

[0005] 2. Background Art

[0006] Information technology (IT) allows valuable information to bedistributed across organizations to groups of information consumersincluding remote employees, business partners and customers. However,organizations have large amounts of information located on disparatesystems and platforms. For maintaining the desired comprehensive view oftheir operations, organizations need to integrate theirs systems. Thenagain, independent configuration for disparate industry standards andtechnologies makes systems integration requirements difficult to meet.Moreover, as the various business applications have diverse features andare tailored to suit the requirements of a particular domain, theirintegration requirements may be also difficult to meet. For example,there are significant integration requirements to make it work whenintegrating a customer relationship management (CRM) application to anexisting system with other applications such as SAP's enterpriseresource planning (ERP) software package, as the CRM is uniquelytailored to the customer care domain.

[0007] Notwithstanding, when addressing their critical informationneeds, organizations often resort to new best-of-the-breed applications(or solutions). To leverage their existing applications, organizationsintegrate their legacy applications with the new solutions, a practiceknown as enterprise application integration (EAI). To this end, softwarevendors have responded by building tools, known as EAI products, alasdifferent tools by different vendors, to automate the integrationprocess.

[0008] Deficiencies in integration and data sharing are indeed adifficult problem of IT environments for any enterprise. The inabilityof organizations to operate as one-organ, rather than separate parts,creates a challenge in information exchange and electronic commerce andresults in economic inefficiencies.

[0009] With conventional solutions, organizations have been using someform of the EAI platform to integrate their application. And they havebeen using a different platform for integrating their data into datawarehouses. Data warehouses integrate data across an organization forreporting and data mining using business intelligence tools like SASInstitute tools.

[0010] The problems with these schemes are that there is no real-timeconnection and interaction between the EAI and data warehousing.Moreover, with relatively static data warehouses the data warehousingcloud is used for analysis but could not participate in the currenttransaction or events that are happening in the organization in realtime. The organization still will end up with two disjointedinfrastructures that cannot leverage each other in real-time (See: FIG.1). Accordingly the present invention addresses these and relatedissues.

SUMMARY OF THE INVENTION

[0011] In accordance with the purpose of the invention, as embodied andbroadly described herein, the invention relates to a framework,architecture, system and method for reducing business transactionlatencies and enabling an enterprise to run as a zero latency enterprise(ZLE). The present invention allows the enterprise to integrate itsservices, applications and data in real time. Namely, an enterpriseequipped to run as a ZLE is capable of integrating, in real time, itsenterprise-wide data, applications, business transactions, operationsand values. Consequently, an enterprise conducting its business as a ZLEexhibits superior management of its resources, operations, supply chainand customer care.

[0012] Underpinning the superior capabilities of ZLE is an informationtechnology (IT) infrastructure that is equipped with and using thehybrid functionality of a ZLE framework. This framework is not a singleproduct or middle ware. Rather, it defines architecture with collectionof products, tools, and services that enables, among others, thereduction of operational latencies in the enterprise. With such hybridfunctionality, an enterprise running as a ZLE can route informationacross various enterprise applications using enterprise applicationintegration technologies. Clearly, the ZLE framework is not just anenterprise integration platform as it can accomplish application anddata integration across the enterprise. Using database extractors,database loaders and application adapters technologies, the ZLE canintegrate data related to the real time operations of the enterpriseinto a data storage cache, also known as operational data store (ODS),and synchronize information across the enterprise using enterpriseapplications integration (EAI) tools. Also, with rules andsynchronization policies implemented in a ZLE hub with the ODS, anyupdates communicated to the ZLE hub from any application across theenterprise can, via the ZLE hub, bring about information synchronizationin all other applications across the enterprise, including its legacyapplications. Information and updates thereof are communicated from theapplications to the ZLE hub by way of adapters. Furthermore, the ZLE canprovide data to business intelligence applications for analysis, and itsupports decision support systems (DSS) and data mart operations as wellas transactional access to up to the minute data by multiple add-on newand legacy enterprise applications.

[0013] As noted, one embodiment of the present invention is a zerolatency enterprise (ZLE) framework in an information technologyinfrastructure of an enterprise that conducts business transactions. Inrelation to business transactions the enterprise experiences a pluralityof events occurring in sites across the enterprise. To reduce theunintended latency in enterprise operations to zero, all organs of theenterprise need to be made aware of business events as they occur, i.e.,in real time. Hence, the ZLE framework is formed with enterpriseapplications installed in relation to respective sites across theenterprise and enterprise application platform configured for enterpriseapplications integration and propagation of indicia of the events acrossthe enterprise, in real time. The ZLE framework is additionally formedwith dynamic central repository configured for real-time loads,extractions, updates and queries. The dynamic central repositoryaggregates information related, in real time, to the plurality of eventswhere a real-time access to the dynamic central repository iscorrespondingly available for the enterprise applications. Hence, a realtime coherent view of the aggregated information is available to theenterprise applications from across the enterprise via the dynamiccentral repository. The ZLE framework is further formed with a serverexecuting and monitoring transactions related to the businesstransactions. The dynamic central repository is operatively connected tothe server so that the business transactions can be conducted across theenterprise with reduced latencies.

[0014] It is noted that the ZLE framework is extensible and availableand enabling the enterprise to become extensible and available as well.It is further noted that the ZLE framework defines a multilevelarchitecture with a hub, wherein the enterprise applications are looselycoupled to the hub and communicating therewith via adapters.

[0015] Another embodiment of the present invention is a system in theinformation technology infrastructure of the enterprise. The systemincludes enterprise applications installed in relation to respectivesites across the enterprise, a ZLE core, clip-on applications tightlycoupled to the ZLE core, and data mining and analysis technologyoperatively connected to the central dynamic real-time data warehouse.The ZLE core is configured with enterprise applications integration andpropagation of information related to the events across the enterprise,central dynamic real-time data warehouse and database management, ZLEservices and transaction processing and monitoring.

[0016] Access to the central dynamic real-time data warehouse anddatabase management is correspondingly available to the enterpriseapplications. A real time coherent view of the information is availableto the enterprise applications from across the enterprise through thecentral dynamic real-time data warehouse and database management. TheZLE services are coupled with the central dynamic real-time datawarehouse and database management and are operatively connected with theenterprise applications. The transaction processing and monitoring isrelative to the central real-time data warehouse and database managementso that the business transactions can be conducted across the enterprisewith reduced latencies. The transaction processing and monitoring at theZLE core is implemented in a server environment that includes a serveror a server cluster.

[0017] The system has a multilevel architecture in which the enterpriseapplications and loosely coupled to the ZLE core via correspondingadapters. One feature of the system is that the central dynamicreal-time data warehouse and database management reduces data dependencybetween the enterprise applications. Another feature is that newenterprise application can be added, wherein the central dynamicreal-time data warehouse and database management provides a historicaccount of events that can be used by the newly added enterpriseapplication.

[0018] In yet another embodiment of the present invention, the methodfor reducing latencies of business transactions enables the enterpriseto run as a ZLE. The method includes instantiating enterpriseapplications installed in relation to respective sites across theenterprise. The method also includes performing a number of steps at aZLE core within the IT infrastructure. These method steps include:instantiating enterprise applications integration and propagation ofinformation related to the events across the enterprise; creating thecentral dynamic real-time data warehouse and database management;instantiating ZLE services that are coupled with the central dynamicreal-time data warehouse and database management and operativelyconnected with the enterprise applications; providing feedbackcapability supported by the dynamic real-time data warehouse anddatabase management and creating transaction processing and monitoringrelative to the central dynamic real-time data warehouse so that thebusiness transactions can be conducted across the enterprise withreduced latencies. The method further includes instantiating clip-onapplications which are tightly coupled to the ZLE core; andinstantiating data mining and analysis that is operatively connected tothe central dynamic real-time data warehouse.

[0019] Advantages of the invention will be understood by those skilledin the art, in part, from the description that follows. Advantages ofthe invention will be further realized and attained from practice of theinvention disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are incorporated in andconstitute a part of this specification, illustrate several embodimentsof the invention and together with the description, serve to explain theprinciples of the invention. Wherever convenient, the same referencenumbers will be used throughout the drawings to refer to the same orlike elements.

[0021]FIG. 1 shows two disjointed infrastructures that cannot leverageeach other in real-time.

[0022]FIG. 2 illustrates the zero latency enterprise (ZLE) model.

[0023]FIG. 3 describes a commercial business with its associated serviceconnections.

[0024]FIG. 4 shows the reality of latencies in operations and ininteractions with and responses to consumers, which prompted enterprisesto seek solutions for reducing latencies.

[0025]FIG. 5 illustrates how an enterprise, running as a ZLE, canconduct instant, personalized marketing (based on known or knowablecustomer preferences) scored and fine-tuned in real time while thecustomer is engaged.

[0026]FIG. 6 is an example of a retail organization.

[0027]FIG. 7 shows a ZLE with all its enterprise customer contact sites(including systems and applications) integrated, responsive andpersonal.

[0028]FIG. 8 illustrates the ZLE model as a blueprint for ZLEarchitecture.

[0029]FIG. 9 illustrates a ZLE framework that defines, in the preferredembodiment, a multilevel architecture (ZLE architecture) centered on avirtual hub.

[0030]FIG. 10 illustrates the core of the ZLE framework.

[0031]FIG. 11 illustrates a ZLE framework with a different applicationserver that can be based on Tuxedo, CORBA or Java technologies.

[0032]FIGS. 12a-c illustrate lookup data that includes data not modifiedby transactions or interactions (i.e., an historic account of prioractivity). FIG. 12a also illustrates how the interaction manager andrules engine can cooperate to produce a prompt or response in connectionwith a particular type of business.

[0033] FIGS. 13, and 13 a-d illustrate clip-on applications such as forfraud detection, customer interaction and personalization, customer datamanagement, narrowcasting, and so on. FIG. 13a further illustrates howthe interaction manager and rules engine can cooperate to produce aprompt or response in connection with a particular type of business.

[0034]FIG. 14 shows bulk data (e.g., real-time customer data) retrievedand delivered from the operatinal data store (ODS) to the analysisapplications.

[0035]FIG. 15 illustrates applications such as Broadvision or Siebel'sCRM (customer relationship management) applications that are logicallyintegrated into (docked) rather than being interfaced with the ZLEframework.

DETAILED DESCRIPTION OF THE INVENTION

[0036] The present invention relates to information technology (IT) and,specifically, to reducing business operations latencies in an enterprisethrough an adaptive IT infrastructure that enables a zero latencyenterprise (ZLE). As a functional and architectural strategy, theinvention contemplates a ZLE framework with a hybrid functionality thatis fashioned by the merger of enterprise application integration (EAI),dynamic real-time operational data warehousing, transaction processingand monitoring, data mining and analysis and a feedback mechanism. (See:FIG. 2 for the ZLE model). The feedback mechanism provides an automaticfeedback of results, produced from the data mining and analysis, to thebusiness transaction paths. The invention further contemplates the ZLEarchitecture, a multilevel architecture that supports the ZLE framework.This scheme enables the enterprise to integrate its services,applications and data in real time. In other words, it enables theenterprise to run as a ZLE.

[0037] To enable one of ordinary skill in the art to make and use theinvention, the description of the invention is presented herein in thecontext of a patent application and its requirements. Although theinvention will be described in accordance with the shown embodiments,one of ordinary skill in the art will readily recognize that there couldbe variations to the embodiments and those variations would be withinthe scope and spirit of the invention.

[0038] The meaning imparted to the terms below and throughout this paperis intended not as a limitation but merely to convey character orproperty relevant to the present invention. Where the terms have aspecial meaning or a meaning that is inapposite to accepted meaning inthe art, the value of such meaning is not intended to be sacrificed towell-worn phrases or terms.

[0039] Enterprise—refers to any organization, including a businessorganization, its subsidiaries, departments, divisions, sections,sectors, groups, branches, channels or like parts; and it can includeany partners, affiliates and associates of the organization. Anorganization includes its resources such as one or more people, systems,databases, policies and more.

[0040] Enterprise-wide or across the enterprise—refers, depending on thecontext, to anywhere within or about the enterprise, in all parts of theenterprise, all over the enterprise, all around the enterprise, acrossall enterprise products, services, and channels, between any sites of orassociated with the enterprise, or at any site of or associated with theenterprise.

[0041] Extensible—refers to any one or the combination of scalable,extendable and expandable. Scalability relates to size, extendibilityrelates to volume and expandability relates to capacity. For example,the ZLE framework and architecture are extensible. With the ZLEframework and architecture, an enterprise is also extensible.

[0042] Scalable—refers to the ability to improve performance byextending the size of an enterprise, a system or an element thereof.Scalability of an enterprise enables it to run as a virtual enterprise(i.e., performing the functions of an entity beyond what is reallythere). For example, scalability allows an enterprise with exhaustedmanufacturing capacity to push production overflows to its partners oraffiliates. Namely, running as a virtual enterprise, the enterprise canextend its existing capacity through manufacturing-on-demand by itsbusiness partners; and the partners have visibility to the enterprise sothat they can stay informed and be prepared to respond. Scalability of asystem involves adding components to the system. Scalability of thesystem allows sizing it for better performance when volume of businesstransactions increases.

[0043] Available—refers generally to an enterprise or system ‘beingthere’ even in the face of failure or absence of a part thereof. Forexample, an enterprise is available when it continues to conduct itsbusiness unimpeded even if a part of the enterprise is shut down. Asystem is available when it continues processing transactions even if itsuffers a component failure.

[0044] Real-time—refers to immediately or almost immediately; or theactual time, nearly the actual time or within seconds from the actualtime during which an event or a process transpires, or pertains to theperformance of a computation or other action nearly or at the actualtime of a related event or process so as to render an instantaneous,up-to-the-second or up-to-the-minute result therefrom.

[0045] Zero Latency—refers to real-time or substantially real time. Interms of a system, zero latency is substantially no delay between thedesired and actual response time. In the context of an enterprise, zerolatency is about real-time or near real-time operations, processing andapplication of information to achieve a competitive advantage, hence theterm zero-latency enterprise (ZLE). As will become evident from thedescription herein, in the context of the present invention, the term‘ZLE’ defines a broader term than the conventional ZLE term. And, toproperly distinguish it from the conventional term, one might use theterm Compaq ZLETM (the present invention was developed at CompaqComputer Corporation in Houston Texas). However, to simplify thediscussion herein, the term ‘ZLE’ is used instead.

[0046] Coherent view—refers to substantial congruity of the views fromany part of the enterprise, or an enterprise-wide view of information,such as data, business transactions and their status, as well as anhistoric account thereof, that is consistent throughout the enterpriseregardless from where in the enterprise the view is obtained. The Viewof information can include access for loads, extractions and queries.

[0047] Loosely coupled applications—refers to applications that canfunction as stand-alone applications and that when integrated with theZLE framework are operationally independent and not relying on eachother for obtaining information although they share that information.The information is accessible by the loosely coupled applications from ashared operational data store (ODS) so that data dependencies betweenrequesting and responding applications are removed.

[0048] Tightly coupled applications—refers to applications that are notstand-alone and are tightly integrated into the ZLE framework. Tightlyintegrated functionality—e.g., event capture, data extraction, rules,workflow, message transports and transformations—becomes part of the ZLEcore functionality.

[0049] Docking—refers to interfacing, integrating or adding (e.g.,adding applications or solutions that extend the IT infrastructurefunctionality and, in turn, that of the enterprise).

[0050] Bulk data—refers to data in mass or at least in a cluster orblock.

[0051] Customer—referred to also as consumer, client, visitor or guest,is any entity, individual, or organization that can receive and consumea value. In a system sense, a customer can be another system orapplication (e.g., an enterprise application is an ‘end-customer’ of theZLE core as will be explained below).

[0052] Value—refers to any service, item for consumption, resource,product, creation, knowledge, information, action, etc. produced by orin association with the enterprise, internally or externally. A value istypically produced for the benefit of the customer.

[0053] Business—refers to any character, undertaking or functionality ofan organization, be it a commercial business or any other type oforganization (e.g., a commercial conglomerate, global charitableorganization, governmental agency, military organization, a localagency, such as law enforcement or emergency response, with affiliationto other local agencies, and more).

[0054] Business transaction—refers to any operation or processassociated with the business. A business transaction can be one or aseries of business transactions, discrete or related to each other. Abusiness transaction can be single or multi-phased, short or ongoing.

[0055] Event—refers, depending on the context, to an event occurringanywhere across the enterprise in the course of conducting the businessof the enterprise or an event occurring in any part of the ITinfrastructure of the enterprise upon commencement, in response to,during or after completion of a business transaction. One type of eventcan produce the other or can occur in combination with the other.Namely, an event can be any commencement or completion of a businesstransaction, any state change of a business transaction, any data entryor data change associated with the business or business transaction, anyinquiry or outcome associated with a business transaction and more. Anevent may produce a result, and the result, if any, may itself be anevent. An event may unlock or prompt the commencement of one or morebusiness transactions. An event may lock or prompt the ending of one ormore business transactions. The locking or unlocking may also be events.An event may be a single occurrence or a series of events. Severalexamples can be provided to illustrate the above. In one example, anevent can be a customer providing a new address or a ‘yes’ answer to aquery about a new address. In a second example, an event and a result,which is a ‘notable’ event, can be the recording of a new prescriptionat a local pharmacy and prompting notification about a new druginteraction related to the prescription from somewhere else. A thirdexample of an event involves an on-line order of a gift certificatesomewhere in the country for a recipient that opened a gift registryaccount in a store somewhere else. In a fourth example involving aseries of events a disaster alert is followed by hazardous chemicalsdata associated therewith. A fifth example involving a series of eventscan be an attempt to return merchandise almost immediately followed by afraud alert or a credit status change. Finally, in a sixth example anevent can be an inventory-level change for an item in a data warehouseor production shop.

[0056] Indicia—refers to any detectable thing associated with an event,including any information related to the event. The information cancontain one or a combination of data, transaction state(s), look-up data(an historic account) and the like. It is noted that the occurrence ofan event can be detected by capturing the indicia of its occurrence.

[0057] Transaction—refers to a collection of operations on the state ofan application. A transaction is typically triggered by a request orinput message that prompts an operation. A transaction trigger mayincludes one or any combination of event, condition and action resultingfrom the transaction (operation). An action can itself be an event or acascade of events.

[0058] Application—refers to a program or software embodied in acomputer readable medium and including computer readable program-codethat causes a computer to perform a certain task. An application canspawn a transaction, and preferably a plurality of concurrenttransactions.

[0059] Services—refers to, in one sense, to enterprise services providedin the course of conducting the enterprise business (See, e.g., FIG. 3which describes a commercial business with its associated serviceconnections). In terms of the IT infrastructure, the term ‘services’refers to any applications that enable the enterprise to run as a ZLE byadding functionality to the IT infrastructure. In the context of the ZLEarchitecture ‘services’ can be one or any combination of applicationsthat provide integration services, ZLE native services, core ISVservices (ISV-independent solution providers), unified rules services,workflow services, message transformation services, extraction,transformation and load (ETL) service and the like. ‘ZLE services’ arecore services and capabilities, where core services include nativeservices and core ISV services. Loosely coupled applications can beconsumers or clients of such services.

[0060] Central repository—refers to a sharable unified capacity such asthe operational data store (ODS) with a relational database managementsystem (RDBMS) in the ZLE framework as defined herein. Although acentral repository can be in a single physical device or located in asingle physical location, the central repository may be configured in adistributed storage system that is nonetheless accessible from acrossthe enterprise.

[0061] As mentioned, the present invention was developed at CompaqComputer Corporation of Houston Texas, and it relates to enterpriseinformation technology infrastructure. The present invention providesCompaq ZLE framework and architecture of an information system as wellas methods for enabling an extensible zero-latency enterprise with anextensible information technology infrastructure.

[0062] Although it would be more accurate to use the term Compaq ZLE™,the term ZLE is used instead for simplicity. For further simplicity, aZLE enterprise equipped with IT infrastructure configured in accordancewith the present invention is referred to in short as ZLE or enterpriserunning as a ZLE.

[0063] ZLE: OVERVIEW

[0064] First, the vision—with zero latency framework, an enterprise canachieve coherent operations, efficient economics and competitiveadvantage. This is in view of the reality of e-commerce, that promptedenterprises to change their business models and to integrate e-commercewith other business models. Moreover, as shown in FIG. 4, the reality oflatencies in operations and in interactions with and responses toconsumers prompted enterprises to seek solutions for reducing latencies.Notably, what is true for a single system is also true for anenterprise—reduce latency to zero and you have an instant response. Inan enterprise running as a ZLE, there can be enterprise-wide recognitionand capturing of business events that can immediately triggerappropriate actions across all other parts of the enterprise and beyond.Along the way, the enterprise gains real-time access to a real-time,consolidated view of the its operations and data from anywhere acrossthe enterprise, and operational inconsistencies are thus eliminated. Theentire enterprise can become more responsive and competitive via aunified, up-to-the-second view of individual customer interactions withany part(s) of the enterprise, their transactions, and their behavior(See, again FIG. 3). Moreover, as FIG. 5 illustrates, an enterpriserunning as a ZLE and using its feedback mechanism can conduct instant,personalized marketing (based on known or knowable customer preferences24) scored and fine-tuned in real time while the customer is engaged 20.This result is possible because of the real-time access to the

[0065] customer's profile (e.g., 24) and enterprise-wide rules andpolicies 22 (while interacting with the customer 20). What is more, aZLE achieves faster time to market for new products and services 26,reduced exposure to fraud, customer attrition, and other business risks.In addition, an enterprise running as a ZLE has the tools for managingits rapidly evolving resources (e.g., workforce) and business processes.

[0066] For example, in a retail organization such as the one shown inFIG. 6, the resources include people, systems, databases and policies.An enterprise running as a ZLE can improve its business and gaincompetitive edge by managing the evolution of its resources. As shown inFIG. 7, in a ZLE all enterprise customer contact sites (includingsystems and applications) are integrated, responsive and personal.Moreover, an enterprise running as a ZLE creates a view of customersdata 30 that is consistent across the enterprise and availablesubstantially simultaneously enterprise-wide.

[0067] Indeed, in a ZLE information becomes available everywhere acrossthe enterprise in real-time. For example, suppose a clerk records aproduct shipment transaction into an enterprise resource at a particularenterprise site. Almost immediately after the ‘enter’ key is pressed,the information is available to analysts via a data mining application,analysis results can be available to the clerk via the feedbackmechanism, including a reporting application, andmanufacturing-on-demand information can be available to suppliers whohave access to the supply chain information.

[0068] Relating again to FIGS. 4 and 5 for a second example, at the timeof contact with a customer, the customer representative of atelecommunication enterprise can suggest a new calling-program based onresults from the data mining application and the customer's profile(such as up-to-date call history, e.g., number of calls per pay period,etc.). As a third example, an insurance provider can introduce newproducts more quickly by establishing a ZLE framework with a dynamiccentral data clearing used by all applications. As fourth example, ahealthcare provider can integrate a patient's medical record and currenttreatment information and use this real-time information to flagmedication conflicts to a remote pharmacist associated with and having areal-time view of the patient's health care information.

[0069] Next, the approach—zero latency involves real-time recognition ofbusiness events, which in turn leads to a more competitive andprofitable business. To become a zero latency enterprise, an enterpriseintegrates, in real time, its data and services. This approach involvesa ZLE solution that simultaneously synchronizes and routes informationacross the enterprise. As a means to that end, enterprise applicationintegration (EAI) provides a mechanism that propagates business eventsacross the enterprise from one system to another. In addition, a centralenterprise cache, or operational data store (ODS) provides the mechanismfor dynamically integrating data into a central repository. This datastore consolidates data from across the enterprise in real time andsupports transactional access to up-to-the-second data from multiplesystems and applications. Unlike an IT infrastructure with aconventional data warehouse, the IT infrastructure of a ZLE allowsoperational systems and applications to access real-time data fromacross the enterprise; and, the real-time data can be made available tobusiness intelligence applications for real-time analysis and feedbackand to data marts and periodic queries.

[0070] Additionally, the aforementioned enterprise-wide integration forenabling the ZLE is implemented in a framework that is beneficiallyextensible. The ZLE framework is extensible in order to allow newcapabilities and services to be added. Furthermore, no matter how ZLE isaccomplished, it needs to encompass and deliver the performance andtransactional integrity of a business-critical operational system.Hence, the ZLE solution provides an operational solution that includeseven more than the merger of enterprise application integration andreal-time data warehousing,.

[0071] It takes architecture to enable a ZLE, and a blueprint for thisarchitecture is described as the ZLE model in FIG. 8. In accordance withthe present invention, the ZLE framework is not about a single product,middleware or monolithic solution. The ZLE framework 10 defines amultilevel architecture (the ZLE architecture) that provides much morethan an integration platform with application integration (EAI)technologies, although it integrates applications and data across anenterprise; and it provides more comprehensive functionality than meredata warehousing, although it supports data marts and businessintelligence functions. As a basic strategy, the ZLE frameworkintegrates applications through the EAI 40, aggregates data through theODS (operational data store) 30, executes in a server 50 transactionsbacked by the ODS 30, enables integration of new applications via theEAI 40 backed by the ODS 30, supports it feedback functionality via thedata mining and analysis 60 and reporting mechanism, and so on.Accordingly, the ZLE framework is fashioned with hybrid functionalityfor synchronizing, routing, caching, data and business intelligence andtransacting enterprise business, in real time, thus enabling coherentoperations and reduction of operational latencies in the enterprise.

[0072] The ZLE framework routes information across various enterpriseapplications using EAI technologies, and aggregates data in anoperational data store (‘ODS’ or ‘data store’ in short) functioning as acentral repository for enterprise-relevant information. The ZLEframework assimilates many existing and new products, tools, andservices that work together to achieve a consolidated, up-to-date viewof state and data that is gleaned from the central repository. Althoughit is not a real time data warehouse system, the ZLE framework supportsDSS (decision support systems) and data mart operations. Thus the datastore is also a central repository and real-time data source for datamining and analysis of enterprise business intelligence applications.Additionally, with the data store capability and centralized creationand management of rules and policies, the ZLE framework allowsconsistent, real-time application of business rules and policies acrossthe enterprise including all its products, services, and customerinteraction channels. Furthermore, the ZLE framework allows developingan enterprise IT infrastructure toward reducing unwanted operationlatencies.

[0073] ZLE: Extensibility (e.g., Scalability) and Availability

[0074] Extensibility (e.g., scalability) and availability are attributesof a ZLE that are made possible by the ZLE architecture. A scalableenterprise can be extended and grow in size. An available enterprise canoperate even in the event of a partial failure of any of its parts. AZLE enterprise is available and can be scalable in real-time, byproviding real-time view of the enterprise to enterprise partners andother enterprise extensions.

[0075] As mentioned, to enable an extensible and available enterprise,extensibility (e.g., scalability) and availability are characteristic ofthe ZLE architecture. The extensibility and availability are devised notso much in terms of massive parallelism or high availabilityconfigurations of architectural components but in terms of how services,applications and data are integrated and how the information is cached.By definition, closely dependent systems are limited in terms ofscalability and availability because of their recurrent inability tofunction without each other or scale independently.

[0076] For example, an e-store may need to access a credit system tocheck a customer rating before completing a transaction (See, e.g.,FIGS. 3-7). Caching the customer rating and transaction data in thecentral repository as opposed to communicating the data betweenapplications loosens application bonds without disrupting theirfunctional integration. In other words, there is ‘breathing room’ sothat faults in one application don't necessarily cascade over the entirearchitecture, and each system can scale at its own pace.

[0077] In another example, an enterprise may need to add agents to andsupport extended operations of its call center. Being scalable, theenterprise can scale its call center operations by outsourcing suchoperations. To allow the enterprise to operate this way, outside vendorsare connected via the ZLE framework to have real-time access to and viewof relevant enterprise-wide data.

[0078] ZLE Architecture

[0079] The ZLE framework defines, in the preferred embodiment, amultilevel architecture (ZLE architecture) centered on a virtual hub,called the ZLE core, as shown in FIG. 9. The preferred ZLE framework 10defines ZLE architecture that serves as a robust system platform capableof providing the processing performance, extensibility, and availabilityappropriate for a business-critical operational system. The enterprisedata caching functionality (DOS) 106 of the ZLE core 102 is depicted onthe bottom and its EAI functionality 104 is depicted on the top. Clip-onapplications 108 are tightly coupled to the ZLE core 102 residing on topof the ZLE core and directly accessing its services. Enterpriseapplications 110, such as SAP's (Systems Applications Products)enterprise resource planing (ERP) application or Siebel's customerrelations management (CRM) application, are loosely coupled to the ZLEcore 102 being logically arranged around the ZLE core and interfacingwith it via application or technology adapters 112. The docking of ISV(independent solutions vendors) solutions such as enterpriseapplications 110, is made possible with the ZLE docking 116 capability.Data mining and analysis applications 114 pull data from the ZLE core102 and contribute result models to it that can be used to drive newbusiness rules, actions, and so on. Although the data mining andanalysis applications 114 are shown residing with systems external tothe ZLE core, they can alternatively reside with the ZLE core 102.

[0080] The ZLE framework includes elements that are modeled after atransaction processing (TP) system. In broad terms, a TP system includesapplication execution and transaction processing capability, one or moredatabases, tools and utilities, networking functionality, an operatingsystem and a collection of services that include TP monitoring.

[0081] At the ZLE Core

[0082] In this embodiment, at the core of the ZLE framework resides aset of ZLE service—i.e., core services and capabilities—as shown inFIGS. 10 and 11. The core services 202 include native services and coreISV services (ISVs are third-party enterprise software vendors). The ZLEservices (121-126) are preferably built around Tuxedo 206, CORBA 208 orJava technologies (CORBA stands for common object request brokerarchitecture). The ZLE services (121-126) are executed on a server,preferably a clustered server platforms 101 such as the Compaq NonStop™Himalaya™ server or the Compaq AlphaServer™ server running the Tru64™UNIX operating system 111 (The Compaq servers are developed by CompaqComputer Corporation of Houston Tex.). The Compaq clustered serverplatforms 101 provide the parallel performance, extensibility (e.g.,scalability), and availability requisite for business-criticaloperations. When either a Tuxedo or CORBA/Java framework 206 or 208 isavailable for use, the CORBA/Java framework can interface to Tuxedoapplications and vice versa.

[0083] Whichever clustered server platform is used in forming the ZLEcore of the illustrated embodiment, the ZLE core components include: 1)Cluster-aware RDBMS 106 for an ODS or a real-time enterprise cache whichin the case of the ZLE is a central repository; 2) transactionsapplication server 101, acting as a robust hosting environment forintegration services and clip-on applications 118; and 3) services121-126 (that will be later described).

[0084] These components are not only integrated, but the ZLE core isdesigned to derive maximum synergy from this integration. Also, many ofthe services at the core of ZLE, such as those governing rules,workflow, and message transformations, are derived from core ISVs. CoreISVs optimize the ability to integrate tightly with and leverage the ZLEarchitecture, enabling a best-of-breed strategy. They contributeessential ZLE services that enable a true Compaq ZLETM.

[0085] It is noted that Compaq®, Compaq ZLE™, AlphaServer™, Himalaya™,NonStop™, and the Compaq logo, are trademarks of Compaq ComputerCorporation of Houston, Tex. True64™ is a trademark of Compaqinformation Technologies Group, L. P., and UNIX® is a trademark of theOpen Group. Any other product names may the trademarks of theirrespective originators.

[0086] Application Server Environment

[0087] As part of the ZLE core, the application server environment (101and 111, FIG. 10) is a key element of the ZLE architecture as itsupports the need for a high-performance application server environmentwith strong transaction monitoring capabilities. In broad terms, theapplication server is a key component of any transaction processing (TP)system that is capable of parallel processing, and supports concurrentOLTP (on-line TP), TP monitoring and management of transactions-flowthrough the TP system. The application server environment advantageouslyprovides a common, standard-based framework for interfacing with thevarious ZLE services and applications as well as ensuring transactionalintegrity and system performance (including scalability andavailability).

[0088] For higher levels of scalability, availability, and dataintegrity, the application server preferably resides on the NonStop™Himalaya™ platform, where it can be based on Tuxedo, CORBA or Javatechnologies for optimum interoperability (See: FIG. 11). CORBA allowsapplications at different locations and developed by different vendorsto communicate via an interface broker called the object request broker.Java is a robust programming language designed for use in thedistributed environment of a network of computers such as the Internet.Java allows applications designed for platform to be portable to anotherplatform (FIG. 11).

[0089] Alternatively, the application server can reside on theAlphaServer™ system running the Tru64UNIX operating system, where it canbe based on off-the-shelf application servers—from companies such asOracle, BEA, and IONA—using CORBA or Java technologies.

[0090] ODS with Cluster-Aware RDBMS Functionality

[0091] Integral to the ZLE core and also very important in the ZLEframework is the ODS with its relational database management system(RDBMS) functionality (106 FIG. 10). The RDBMS is optimized for massivereal-time transaction and loads, real-time queries, andbatch-extraction. The cluster-aware RDBMS is able to support thefunctions of an ODS contaning current-valued, subject-oriented, andintegrated data reflecting the current state of the systems that feedit. Ideally, it can also function as a message store and a state engine,maintaining information as long as required for access to historicaldata. It is emphasized that ODS is a dynamic data store and the RDBMS isoptimized to support the function of a dynamic ODS.

[0092] The cluster-aware RDBMS component of the ZLE core in thisembodiment is either the NonStop™ SQL database running on the NonStop™Himalaya™ platform or Oracle Parallel Server running on the Tru64 UNIXAlphaServer™ system. In supporting its ODS role as a real-timeenterprise cache, the RDBMS contains preferably three types ofinformation: state data, event data and lookup data. State data includestransaction state data or current value information such as a customer'scurrent account balance. Event data includes detailed transaction orinteraction level data, such as call records, credit card transactions,Internet or wireless interactions, and so on. Lookup data includes datanot modified by transactions or interactions (i.e., an historic accountof prior activity). See: FIGS. 12a-12 c.

[0093] Overall, the database is optimized for application integration aswell as real-time transactional data access, and updates including foranalysis and business intelligence. For example, a customer record in aZLE data store (i.e., ODS) might be indexed by customer ID (rather thanby time, as in a data warehouse) for easy access to a complete customerview. In this embodiment, key functions of the RDBMS includes dynamicdata caching, historical or memory data caching, robust message storage,state engine and real-time data warehousing.

[0094] The dynamic data caching function supports a dynamic, real-timeODS function. For a dynamic, real-time ODS, the RDBMS employs dynamicdata caching to aggregate, cache and allow real-time access to real-timestate data, event data and lookup data from across the enterprise.Advantageously, this function, for example, obviates the need forcontacting individual information sources or production systemsthroughout the enterprise in order to obtain this information. As aresult, this function greatly enhances the performance of the ZLEframework.

[0095] The historical data caching function allows the ODS to alsosupply a historic account of events that can be used by newly addedenterprise applications (or clip-on applications). See, e.g., FIGS. 12aand 12 b. Typically, the history is measured in months rather thanyears. The historical data is used for enterprise-critical operationsincluding for transaction recommendations based on customer behaviorhistory

[0096] The robust message store function supports the EAI platform forZLE hub-based publish and subscribe operations (that are explained inmore detailed in the aforementioned related copending U.S. applicationSer. No. _______, entitled “ZLE Enriched Publish/Subscribe”). Formessage publishing (pushing to ODS) and message subscription (pullingfrom ODS and dissemination), the RDBMS caches and queues messages forsubscribers (relating for example, to specific events and theirresults). Performing publish and subscribe through the relationaldatabase enables the messaging function to leverage the parallelism,partitioning, and built-in manageability of the RDBMS platform.Priority, first-in/first-out, guaranteed, and once-and-only-oncedelivery are all supported in this platform.

[0097] The state engine functionality allows the RDBMS to maintainreal-time synchronization with the business transactions of theenterprise. The RDBMS state engine function supports workflow managementand allows tracking the state of ongoing transactions (such as where acustomer's order stands in the shipping process) and so on.

[0098] The real-time data warehousing function of the RDBMS supports thereal-time data warehousing function of the ODS. This function can beused to provide data to data marts and to data mining and analysisapplications.

[0099] Core ZLE Services

[0100] In an embodiment of the ZLE framework, the ZLE core servicesreside on top of the transactional application environment and use itsTuxedo or CORBA/Java framework as well as its underlying parallelcomputing platform (server). A broad range of basic services isincorporated into the ZLE architecture. These include services forbusiness rules enforcement, message transformation, workflow and Bulkdata extraction. In other words, as shown in FIG. 10, the servicesinclude: 1) rules service 121, for event-driven business rules creation,analysis and enforcement. The business rules enforcement service isprovided for defining and applying enterprise rules and policies acrossthe enterprise; 2) workflow (process-flow) service 122 for supportingglobal business transactions across multiple systems and for mapping andcontrolling the flow of business transactions across the enterprise; 3)message transformation service 123 for efficiently integrating diversedata from any number of disparate sources applications; 4) parallelmessage router and inserter service 124 for high performance,high-volume routing, and insertion of data into the ODS and other ZLEservices and applications; 5) event capture service 125 for supportingthe enterprise-wide business; and 6) extraction, transformation, andload (ETL) service 126, to move bulk data into and out of the ODS andacross database and platform boundaries. The bulk data extractionservice is for uploading aggregated batched transactions back into theODS, for uploading aggregated batched transactions cak into the ODS, andfor moving huge volumes of data quickly out of the ODS to productionsystems, business intelligence systems, and so on. These services andothers, can be provided by Compaq, the originator of the ZLE framework,or ISVs.

[0101] There is a great deal of synergy between the services as well.For example, the rules service can be used by the other services withinthe ZLE core and any clip-on and enterprise applications that anenterprise may add, for providing enterprise-wide uniform treatment of abusiness transaction based on enterprise-wide uniform rules.

[0102] Message Routing

[0103] A powerful message routing and insertion capability (124 FIG. 13)is needed for routing high volumes of messages through the ZLEarchitecture. This capability can include content-based routing and useof the ODS (RDBMS) as a centralized message store and queuing system forefficient publish/subscribe message distribution. Essentially, thismessage routing and insertion capability is routing between the internalcomponents of the ZLE core. Hence, although the ZLE framework supportsmessaging oriented middleware (MOM), such as the IBM MQSeries software,this capability differs from the functionality of routing and queuingsystems that move messages from application to application (such as theIBM MQSeries software; IBM-Information Business Machines, Inc, ofArmonk, N.Y.).

[0104] Rules Service

[0105] The rules service (See, e.g., 121 FIG. 10 and FIG. 13) enableswriting business rules using graphical user interface or syntax like adeclarative, English-language sentence. Additionally, the rules servicefinds and applies the most applicable business rule upon the occurrenceof an event, and arrives at the desired data/answer as rapidly aspossible which is uniform throughout the entire enterprise. Hence thisservice may be referred to as the uniform rules service. This serviceallows the ZLE framework to provide a uniform rule-driven environmentfor flow of information and supports it feedback mechanism.

[0106] To that end, the ZLE core incorporates an inference-based rulesengine 121 FIG. 13a (e.g., Brokat Blaze Advisor) that quickly andefficiently finds the appropriate business rule, regardless of thecomplexity of the rules or the size of the rules set. The rules servicealso integrates the rules and policies of an enterprise in a centralizedlocation (ODS at the ZLE hub), next to the message stream. This positionallows it to drive workflow, facilitate rapid changes to the rules, andensure consistent application of business rules in all systems acrossthe enterprise (e.g., call centers, e-commerce sites, POS applications,and so on).

[0107] In this embodiment, the rules engine in the ZLE framework is aJava implementation that has been wrapped in the interaction manager(131 FIG. 13a) to execute on top of this parallel, available middlewareof the framework. (The interaction manager will be explained later.Middleware products automate much of the basic connectivity. Thus,instead of, for example, building point-to-point links, middlewareproducts automate the basic connectivity involved in applicationsputting data onto a CORBA object request broker (ORB). This allows thedata to be use by any CORBA-compliant application.) The rules engine ispreferably a pure Java-based full-inference engine that is flexible,capable of GUI (graphics user interface) driven rules and is minimallyimpacted by the size of the rules set. In addition, the rules engine ispreferably non-sequential and non-iterative.

[0108] Scenarios in which the interaction manager and rules enginecooperate to produce a prompt or response can be better explained inconnection with a particular type of business (See: FIG. 12c and FIG.13a). For example, in a retail business where customer can engage inmultiple transactions with the enterprise and each transaction mayinvolve a unique identity of that customer. From the historic account ofcustomer interaction(s) at the ODS, the interaction manager canrecognize each of the unique identifiers as being associated with thesame customer. Via the rules engine the interaction manager can providea rule-based response in view of this finding (such as: thisidentification belongs to a customer that is not to be serviced afterone or more fraudulent transaction attempts). This is so, even if thecustomer attempts to remain anonymous and uses a different channel ofcommunication with the enterprise (See, e.g. FIGS. 7, 12a-c, 13 a and 13b).

[0109] Workflow Service

[0110] The process-flow (workflow) service (122 FIG. 10) manages theflow of business transactions and processes between multiple systems andapplications that are integrated via the ZLE framework and may take onlyseconds or up to days to execute. This entails monitoring and managingongoing transactions as well as ensuring the correct flow of businesstransactions. For example, when a customer opens an account, disputes acharge, returns a product, or even changes an address, such action(event) launches a series of sequential business transactions. Theworkflow (process-flow) service leverages the state engine capabilitiesof the ZLE core database to track the state of the transaction—andprovide visibility into its progress—over the ensuing hours, days, andweeks it takes to run its course. The workflow service in the ZLEframework is, for example, an EJB (Enterprise Java Bean, Java 2enterprise edition (J2EE)) compliant service running on parallel,available application servers that can store its workflow as XML datastructures. XML stands for eXtensible Markup Language. It is a subset ofSGML (Standard Generalised Markup language) and was originally designedto make it easier for Internet users to interchange structureddocuments. XML schema expresses shared vocabularies and defines thestructure and content of XML documents (using Document TypeDefinitions).

[0111] Message Transformation Service

[0112] By mapping differences in message syntax, semantics, and values,the message transformation service (123 FIG. 10) within the ZLE coreassimilates diverse data from multiple sources for distribution tomultiple diverse destinations. The message transformation serviceenables content transformation and content-based routing, thus reducingthe time, cost, and effort associated with building and maintainingapplication interfaces.

[0113] In this embodiment the graphic interface in the NonStop™ DataTransformation Engine (based on Mercator) streamlines this taskspecially when complex data formats, such as EDI (electronic datainterchange format X12, EDIFACT), S.W.I.F.T. (for financialtransactions), HL7 (healthcare data formal), and ACORD (insurance dataformat), need to be transformed into a standard or common format. Astandard or common message format allows various applications tounderstand the event and its content regardless of how different theyare.

[0114] Parallel Message Router and Inserter Service

[0115] The high-performance parallel message router and inserter service(124 FIG. 10) within the ZLE core moves large volumes of messages to theODS (where they are captured with minimal transformations) or to otherservices in the ZLE core. As discussed previously, the database (ODSRDBMS) can act as a database for storing transactions in SQL tables oras a message store-caching and queuing messages for publish/subscribedistribution. Constantly refreshed information, such as stock prices ordata on inventory levels, can be inserted into the ODS and thenpublished to the appropriate subscriber. The router and inserterfunction leverages the parallelism of the ZLE platform to propagate highvolumes of messages to the database and elsewhere within the ZLEframework.

[0116] Extraction, Transformation, and Load (ETL) Service

[0117] The ETL service (126 FIG. 10) within the ZLE core enables largevolumes of data to be moved quickly and reliably in and out of thedatabases (often across database and platform boundaries) for use byanalysis or operational systems as well as by clip-on applications.

[0118] Leveraging the ZLE Core

[0119] In the ZLE framework scheme, the ZLE core (or ZLE hub) is avirtual hub for various specialized applications that can clip on to itand are served by its native services. Any specializedapplications—including those that provide new kinds of solutions thatdepend on ZLE services—can clip on to the ZLE core. The ZLE core is alsoa hub for data mining and analysis applications that draw data from andfeed result models back to its ODS. Indeed, the ZLE framework combinesthe EAI, ODS, OLTP (on-line TP), data mining and analysis, automaticmodeling and feedback, thus forming the touchstone hybrid functionalityof every ZLE framework. To this functionality others can be addedincluding the functionality of native and core ISV services and ofclip-on and enterprise applications. Moreover, the ZLE hub enables anarray of enterprise applications—from ERP to legacy OLTP applicationsand from database to Web server applications—to interface to and becomepart of the ZLE framework. The ZLE framework provides the means forpulling together and integrating all of these third-party applications.

[0120] Clip-On Applications

[0121] Clip-on applications, literally clip on to, or are tightlycoupled with, the ZLE core (See, e.g., 118 FIGS. 9-11; and in moredetail 131-135 FIG. 13). They are not standalone applications in thatthey require the substructure of the ZLE core and its services (e.g.,native core services) in order to deliver highly focused, business-levelfunctionality of the enterprise. Clip-on applications providebusiness-level functionality that leverages the ZLE core and customizesit for specific purposes, such as real-time fraud detection (designed toleverage the rules service within the ZLE core). Clip-on applicationsenable the addition of unique (custom) services that can leverage theZLE core's real-time environment and application integrationcapabilities. Thus, ISVs (such as Trillium, Recognition Systems, andMicroStrategy) as well as the originator of the ZLE framework (CompaqComputer Corporation) can contribute value-added clip-on applicationssuch as for fraud detection, customer interaction and personalization,customer data management, narrowcasting of notable events, and so on, asshown in FIG. 13. A major benefit of clip-on applications is that theyenable enterprises to supplement or update its ZLE core native or coreISV services by quickly implementing new services. Examples of clip-onapplications include interaction manager 131, narrowcaster 132, campaignmanager 133, customer data manager 134 and more. The following describesthese examples in some detail.

[0122] Interaction Manager

[0123] As shown in FIG. 13a, the interaction manager application 131 (byCompaq Computer Corporation) leverages the rules engine 121 within theZLE core to define complex rules governing customer interactions acrossmultiple channels. The Interaction manager also adds a real-timecapability for inserting and tracking each customer transaction as itoccurs so that relevant values and more can be offered to consumersbased on real-time information.

[0124] Narrowcaster

[0125] The narrowcaster application 132 preferably uses MicroStrategysoftware that runs against the RDBMS of the ODS in order to notify anotable event (hence it is also called notification application).Notable events are detected within the ZLE framework in real-time. Then,sharing data (in the ODS) that the interaction manager and rules enginehave used to assert the notable event, the narrowcaster selectivelydisseminates a notification related to such events. The notification isnarrowcasted rather than broadcasted (i.e., selectively disseminates) toterminals, phones, pagers, and so on of specific systems, individuals orentities in or associated with the enterprise (See, e.g., FIG. 13c). Forexample, if a transaction that poses a higher risk to the enterprise ora customer of the enterprise is uncovered, an entity in or associatedwith the enterprise is notified that this transaction has beenidentified as presenting such risk before the transaction is completed.Thus, if for instance a call center operator (or an automated system) istransacting with a customer and the transaction poses a risk of fraud,the narrowcaster notifies the call center operator (or automatedsystem), in real-time, before that transaction is completed (so thatservice can be timely denied).

[0126] Campaign Manager

[0127] The campaign manager application (133 FIG. 13d) can operate in arecognition system such as the data mining and analysis system (114,FIG. 1) to leverage the huge volumes of constantly refreshed data in theODS of the ZLE core. The campaign manger directs and fine tunescampaigns in real time based on real-time information gathered in theODS. See: FIG. 13c.

[0128] Customer Data Manager

[0129] In this embodiment, the customer data manager application (34FIG. 13) leverages Trillium's customer data management software tosynchronize, delete, duplicate and cleanse customer information acrosslegacy systems and the ODS at the ZLE core's in order to create aunified and correct customer view.

[0130] Building the ZLE Framework

[0131] When all these concepts, requirements, and components of the ZLEframework are viewed together, a picture emerges of an end-to-endextensible multilevel architecture that integrates data, applicationsand business processes from across the enterprise in real time tosupport real-time actions. As outlined before, the ZLE framework bringsnew extensibility (e.g., scalability), availability and, with the ODS asa central repository, performance independence to enterprise functions.The ZLE framework allows integration of new types of applications thatmuch like pre-existing applications partake in the real-time data andapplication integration.

[0132] To this end, the present invention provides a proven blueprint toimplement the vision. That is, the present invention as describedherein-above and below provides a blueprint for building the ZLEframework (See, e.g., FIG. 8).

[0133] Building a ZLE framework around a transactional applicationserver means gaining all the hosting benefits of the application server.In this embodiment of the ZLE framework, that means the ability to runparallel tasks that are dynamically load balanced across nodes on theNonStop™ Himalaya™ server or on the AlphaServer™ system running theTru64 UNIX operating system. This also means the ability to monitortransactions (such as the above-mentioned business transactions) andrestart them in the event of failure, manage transaction boundaries,manage queues, and so on.

[0134] The ZLE core services, such as rules and messaging, execute ontop of this environment, which means that they inherit all theseadvantages. Equally important, a transactional application serverenvironment provides a common framework with which these services or anyother applications interface and through which they interact with eachother notwithstanding their disparate design platforms or features (asmentioned, the various application can include web servers, ERPapplications, and any legacy applications and databases). Hence, an ITinfrastructure that is based, for example, on Tuxedo technology is ‘athome’ when integrated with a ZLE framework and its services via Tuxedo.The same holds true for CORBA and Java (or any compatible broker)technology-based infrastructures. Essentially, it boils down toselecting the framework that provides the highest level of comfort andthe maximum amount of flexibility for any given IT infrastructure—thebasic functionality is the same in either case. The scenario shaped bythe ZLE framework is compelling in that it promises reduced operationalinconsistencies, instant awareness of business events, increasedcompetitiveness, and more.

[0135] ZLE Framework Takes Best-of-Breed Applications

[0136] The ZLE framework represents something new in the IT industry. Byproviding an open integration platform for best-of-breed applications,the ZLE framework enables enterprises to leverage the functionality of awealth of ISV applications on top of a robust ZLE platform. Suchapplications are able to draw on the strengths of the ZLE architecture(parallelism, massive scalability, continuous availability, and so on)and add their own value to it.

[0137] ISV applications can be loosely or tightly coupled, to become alogical or integral part of the ZLE core functionality, respectively.Tight coupling of applications on a large a scale as provided in the ZLEframework has not been seen before, and certainly not in the EAI world.But it is in EAI where it can make the most difference. This is because,with EAI supporting tightly integrated core services functionality, theZLE framework can benefit from a vast range of tightly integratedfunctionality—from rules and workflow to message transports andtransformations—that is required for the business of the enterprise. Foran enterprise, this scheme translates into the best possible solution,as it is based on the best-of-the-breed applications in the industry.For example, a customer can sign their name once, and the signature orinformation or transaction unlocked with that signature is availableacross the enterprise for any best-of-the-breed application integratedwith the ZLE core. In other words, there is no need to obtain from thecustomer an additional signature for other applications handling otherinteractions with this customer through other channels.

[0138] Data Mining and Analysis Tools

[0139] Usually, databases are configured either for OLTP (on-linetransaction processing) or for OLAP (on-line analytic processing) anddata analysis in order to optimize and maximize database performance.However, in ZLE solutions there is a need to perform mixed workloads,OLTP and OLAP, concurrently against the same ODS. Namely, the ODS is notonly for OLTP. This adds a significant value to the ZLE solutions.Through data mining and analysis applications, and knowledge discoveryapplications (e.g., OLAP applications) running against the same ODS, theZLE solutions support concurrent operations for OLTP as well as forOLAP. Thus, the ZLE framework enables integration with the ZLEarchitecture of data mining and analysis, OLAP, or other similarprograms so that such tools can receives all the data they needs fromthe ODS (without impeding database quality of service performance).

[0140] Data mining, OLAP, and other knowledge discovery applicationsleverage the data contained within the ZLE core for enterpriseintelligence purposes. Such applications subsequently feed backknowledge in the form of actionable models into the ZLE framework. Asshown in FIG. 14, bulk data (e.g., real-time customer data) is retrievedand delivered from the ODS 106 to the analysis applications 114 via theETL service (not shown here). An analysis program can produce resultmodels 140 based on information gleaned from the data; and such modelscan be delivered as feedback to the unified rules service of the ZLEcore. For example, based on buying habits and purchase history, whichcan be used to guide future interactions, an analysis program can createa result model that extrapolates for any customer (or group ofcustomers) the customer's (or customers') likely future purchases. It isalso possible to directly query the ODS through an open interface suchas SQL, Open Database Connectivity (ODBC) or Java Database Connectivity(JDBC) when this is the preferred access method.

[0141] Extending the ZLE Architecture

[0142] The ZLE core architecture cannot exist in a vacuum; and be ableto evolve with changes in the business environment of the enterprise. Tointegrate or interface with a wide variety of existing or new enterpriseapplication environments, the ZLE architecture provides adapters (See,e.g., 110 & 112 FIG. 9). The adapters enable normalized messaging forexchanges among standard applications (such as SAP, PeopleSoft, popularWeb server applications, and so on) as well as exchanges with customapplications. There are other architectural and functional requirementsthat the adapters support, including allowing, for example, legacyenvironments and diverse databases to join the ZLE framework.Additionally, the ZLE architecture should be able to easily interfaceand share data with enterprise intelligence systems (also termedbusiness intelligence systems). These are systems that can retrieveinformation from the ODS, perform data analysis, fcreate result models,and then feed them back to create new business rules. For example, acustomer's likelihood to buy a product can be measured and used toinform a business rule governing future interactions with thatindividual.

[0143] Enterprise applications are standalone, third-party enterpriseapplications that are loosely coupled to the ZLE core, the clip-onapplications and other third party enterprise application (or ISVsolutions). When so interfaced, an enterprise application becomes alogical part of the ZLE framework and shares that data with all theother applications through its ODS.

[0144] Docking Applications to the ZLE Framework

[0145] Third-party enterprise applications (specialized ISV solutions),such as PeopleSoft, SAP's ERP or Siebel's CRM applications, can “dock”on the ZLE core via adapters, which are available for Tuxedo-based,CORBA-based or Java-based ZLE, MOM (message oriented middleware) andlike platforms. As mentioned, these applications differ from the tightlycoupled clip-on applications in that they can exist alone, without thebenefit of the ZLE framework. However, their value is increasedimmensely by integration with the framework. In some cases, theseapplications are the “end-consumers” of the ZLE architecture. In others,they provide much of its fodder in the form of information andspecialized procedures of the enterprise. Typically, as they integrateor interface via the ZLE framework with other applications and systemsacross the enterprise they play both roles—i.e., taking and providinginformation in real time.

[0146] In this embodiment, docking enterprise applications can fall intotwo categories: interfaced solutions and integrated solutions.Interfaced solutions use industry-standard adapters and can publish anevent to the ZLE framework or apply such event from the ZLE frameworkback to the application. These applications are relatively passive andnoninvasive to the overall ZLE framework. Integrated solutions can becustom-made to directly utilize ZLE core services via a request-responsemodel. These applications are specialized within the overall ZLEframework.

[0147] Applications such as Broadvision or Siebel's CRM applicationsthat are designed for customer information management, can be morereadily logically integrated into rather than being interfaced with theZLE framework (See, e.g., FIG. 15). Hence they are able to contributesignificant value to as well as receive significant value from the ZLEframework. For example, Siebel's CRM application benefits from theunified rules service and the ODS of the ZLE core and, by the sametoken, it enhances the support of data mining and analysis applicationsin the ZLE framework.

[0148] ZLE Adapters

[0149] ZLE adapters tie enterprise applications to the ZLE framework.Their job is the traditional EAI job of mapping any proprietaryapplication program interface (API) to the native APIs and protocols(CORBA, Java, or Tuxedo) of the ZLE framework. In most cases, theadapter resides on the application platform and not on the ZLE coreplatform. Typically also, three types of adapters are used: application,data and technology. The application adapters are typically eitherready-made, fast, thin adapters for Oracle, PeopleSoft, SAP' ERP,Siebel's CRM, and other applications, or they are custom adapterscreated with development kits for custom and legacy applications. Dataadapters interface directly to a data source like a file or database.Technology adapters are essentially gateways to disparate transaction ormessaging environments such as IBM CICS MQSeries (CICS is customerinformation control system). Application and custom adapters fromActional Corporation normalize messaging between the ZLE core andenterprise applications, be it standard, packaged or customapplications. Technology adapters enable interoperability with legacyenvironments (such as IBM's CICS i.e., customer interface controlsystems, and Compaq's Pathway), databases, Web server application, andso on.

[0150] While application adapters interface with existing APIs, data andtechnology adapters are used to pull data directly from an IBM MQSeriesmessage queue or an Oracle database table. Application adapters can beconstructed so that no modifications are required to the targettransaction monitor or database and so that all security mechanisms canstay intact. Some adapters are targeted for interchange of data withbusiness networks, such as S.W.I.F.T. for financial business, Healthnetor HL7 for healthcare business, and more.

[0151] ZLE Framework in Operation

[0152] The ZLE framework supports application and data integration andfashions unique hybrid functionality. This section presents someexamples of how application and data integration work together in theZLE framework in real time in the real world. EAI tools typicallyperform message functions, while database and application servers are incharge of transactions and data functions. The ZLE framework merges bothas well as other functions that are unique to the ZLE framework.

[0153] The ZLE framework is designed to perform numerous functions insupport of an enterprise business. Here is how it handles some of thesefunctions in various business scenarios.

[0154] Messaging Functionality

[0155] Messaging functions in the ZLE framework may involve a simplemessaging scenario of an EAI-type request-response situation in which acall-center application requests information on a particular customerfrom a remote billing application. The call-center application issues aTuxedo call that the transformation service in the ZLE core maps to aTuxedo call for communicating with the remote application. Billinginformation flows back to the call center through a messaginginfrastructure.

[0156] Another scenario might involve publish and subscribe, that alsoinvolves the EAI function. In that scenario, several applicationssubscribe to the ZLE framework, asking for specific information whenevera certain event occurs. These applications could be Web server, callcenter, or fraud detection applications in search of changes in aconsumer's credit status; or they could be electronic catalog or supplychain applications dependent on receiving the most current inventorystatus. When the event takes place, an adapter publishes the change tothe ZLE framework, which then formats the messages correctly and pushesthem to the subscribing applications, where they are filtered throughthe application adapters.

[0157] A more advanced scenario requires message routing. Here the rulesand workflow services of the ZLE core intervene to determine whereparticular messages must be routed based on content and predefinedworkflow process.

[0158] Data Functions

[0159] As mentioned above, data functions in the ZLE framework,particularly those of the ODS, include but are not limited to only oneof the functions such as real-time data warehouse or OLTP applicationsbuilt on an RDBMS and application server. The ODS is optimized, via theETL service of the ZLE core, for extracting, aggregating, and thenmoving large bulk data to analysis applications, data marts, and more.While not necessarily optimized for large volumes of ad hoc queries, theODS make available its granular, real-time data to such queries, whennecessary. For example, the ODS can be open to queries when there is noaggregate database available to answer a one-time business intelligenceor decision support query, or when a query requires a data relationshipthat is denormalized when other business systems are loaded.

[0160] In a simpler scenario, access to information in the ZLE frameworkby OLTP or enterprise intelligence applications is supported viastandard ODBC or JDBC calls from a remote system to the ODS. Similarly,an OLTP application (such as a Tuxedo application) can reside on the ZLEcore platform to directly access the ODS with SQL statement anddistribute data to its clients via CORBA, Java or Tuxedo mechanisms.

[0161] Hybrid Functionality

[0162] The ZLE framework achieves its unique qualities through itshybrid functionality. The ZLE framework combines the EAI, RDBMS (ODS)transaction processing and monitoring, data mining and analysis andfeedback to form its hybrid functionality. And each of these elementsoffers unique functionality as described herein. For example, the ZLEarchitecture supports cached request-response functionality in whichresponses from applications are cached to the ODS as they occur (i.e.,the ODS receives and stores real-time responses). These responses can beinventory-level changes, current account balances, etc. The requestingapplication draws the responses from the ODS, not directly from theremote application. Consequently, the dependencies between therequesting and responding applications are largely removed. And so, theresponding application can go down, but current or near-currentinformation is still available in the ODS for continuous operation. Forexample, on the subsequent failure of a corresponding application,customers can still get answers or supply chain applications staycurrent because the responses have previously been cached in the ODS.Moreover, changes made to the data can be supplied to the ODS andstacked on reliable queues to be applied to the responding system, whenit becomes available. In other words, with the ODS at the ZLE core theenterprise can achieve its availability attribute even in the face offailing information production applications.

[0163] The ZLE framework also supports database publish and subscribe.That is, data can be published to the ODS, for example, in an XMLmessage, for formatting and insertion into a database table. It can thenbe routed out of the ODS to multiple subscriber systems. In this way,the innate parallelism, scalability, and reliability of the database canbe leveraged, along with its management capabilities, to ensure anefficient flow of subscriber messages. Of course, the currentinformation contained in the database tables is also available for adhoc querying or for bulk shipment to analytic applications, data marts,and so on. Other publish and subscribe products on the market contain adata store for the queues, but they are not relational. And, unlike theZLE architecture, they do not allow the end user to access these datastores through standard SQL syntax or change the data through OLTP.

[0164] Return on Cache

[0165] Perhaps even more valuable is the ability of the ODS to cachedata that can be used to enrich the messages—i.e., for request responseor publish subscribe—that pass through the ZLE framework. For example,the response to a request for “last customer transaction” can beenriched by change of address or change of marital status informationcontained in the ODS as the response flows through the framework.

[0166] Similarly, information cached in the ODS for distribution tosubscribers can pick up additional data that has been cached there byother systems. For example, a business-to-business customer wants tomake an online purchase. As the ZLE architecture pulls together currentinventory and pricing information, it can enrich it with personalizedcustomer-specific data from its data store regarding special offers onrelated products—information that is invisible to the inventory system.

[0167] Addressing Platform Requirements

[0168] The ZLE framework presupposes a set of platform and technologyattributes. By including these attributes in the ZLE framework, thevision of recognizing events in real time and triggering immediate,appropriate actions across the enterprise can be more readily realized.

[0169] As a basic attribute, the ZLE framework is capable of handling acomprehensive mix of data, messaging, and functionality. In addition tothis challenging mix, the ZLE framework includes a robust applicationserver functionality that is needed for strong transaction management.The ZLE framework is capable of supporting all leading transports andadapters. The ZLE framework is further capable of supporting parallelexecution of functions because real-time operations start with real-timeexecution. For a real-time consolidated view of the enterprise business,the ZLE framework provides a single, manageable view of applications anddata. Moreover, with inherent extensibility (e.g., scalability) andsupport for 24×7 operations, a ZLE framework can expand gracefully andprovide the continuous operations that characterize a business-critical,revenue-enabling system.

[0170] To this end, the cluster platforms—NonStop™ Himalaya™ server orAlphaServe™ system running the Tru64™ UNIX™ operating system—arepreferably chosen to provide parallel execution of key functions inorder to ensure real-time operations. Moreover, the ability to support asingle system image across multiple nodes is built into the NonStop™Himalaya™ platform. The cluster architecture of these platforms andtheir associated database and application server environments enabletheir massive scalability, exceptional performance even under peakloads, and unrivaled availability for 24×7 operations.

[0171] Finally, the ZLE framework's open architecture enables coreservices and plug-in applications to be based on best-of-breed solutionsfrom leading ISVs. This, in turn, ensures the strongest possible supportfor the full range of data, messaging, and hybrid demands.

[0172] In Summarry

[0173] The present invention contemplates enabling a ZLE that is allabout competitive advantage. The ZLE framework keeps information frommyriad enterprise systems refreshed, ready for consolidation, andavailable for real-time deployment in decision-making, CRM, inventorymanagement, and marketing campaigns. The ZLE framework realizes thisvision by creating an amalgamation of many functions to fashion hybridfunctionality. This hybrid functionality allows the combining andhot-caching of information from across the enterprise in real time, aswell as providing uniform rule-driven, workflow-informed architecturefor the flow of information and breaking down performance dependenciesbetween applications. This hybrid functionality also enables new typesof applications that could not exist without real-time data andapplication integration.

[0174] The ZLE framework is designed to leverage best-of-the-breed toolsinto customized, integrated solutions for applications and dataintegration. The ability of the ZLE architecture to perform differenttypes of functions and process different workloads in parallel andaround the clock (24×365), without the need for maintenancedowntime—with the added functionality of clip-on applications frombest-of-the-breed ISVs—is what unleashes the incredible businesspotential of any ZLE that builds the ZLE framework into their ITinfrastructure.

[0175] Although the present invention has been described in accordancewith the embodiments shown, variations to the embodiments would beapparent to those skilled in the art and those variations would bewithin the scope and spirit of the present invention. Accordingly, it isintended that the specification and embodiments shown be considered asexemplary only, with a true scope of the invention being indicated bythe following claims and equivalents.

What is claimed is:
 1. A zero latency enterprise (ZLE) framework in aninformation technology infrastructure of an enterprise that conductsbusiness transactions in relation to which the enterprise experiences aplurality of events occurring in sites across the enterprise, the ZLEframework comprising: enterprise applications installed in relation torespective sites across the enterprise; enterprise application platformconfigured for enterprise applications integration and propagation ofindicia of the events across the enterprise, in real time; dynamiccentral repository configured for real-time loads, extractions, updatesand queries, the dynamic central repository aggregating informationrelated, in real time, to the plurality of events, a real-time access tothe dynamic central repository being correspondingly available to theenterprise applications so that a real time coherent view of theaggregated information is available to the enterprise applications fromacross the enterprise via the dynamic central repository; a serverexecuting and monitoring transactions related to the businesstransactions, the dynamic central repository being operatively connectedto the server so that the business transactions can be conducted acrossthe enterprise with reduced latencies.
 2. The ZLE framework of claim 1enabling the enterprise to run as a ZLE.
 3. The ZLE framework of claim 1being extensible and available and enabling the enterprise to becomeextensible and available.
 4. A zero latency enterprise (ZLE) frameworkin an information technology infrastructure of an enterprise thatconducts business transactions in relation to which the enterpriseexperiences a plurality of events occurring in sites across theenterprise, the ZLE framework comprising: enterprise applicationsinstalled in relation to respective sites across the enterprise;enterprise application integration technology configured as a platformfor integrating the enterprise applications and propagating indicia ofthe events across the enterprise, in real time; dynamic centralrepository configured as a dynamic real-time operational data store(ODS) with a relational database management system (RDBMS) for real-timeloads, extractions, updates and queries, the dynamic central repositoryaggregating information related, in real time, to the plurality ofevents, a real-time access to the dynamic central repository beingcorrespondingly available to the enterprise applications so that a realtime coherent view of the aggregated information is available to theenterprise applications from across the enterprise via the dynamiccentral repository; ZLE services coupled to the dynamic centralrepository and operatively connected with the enterprise applications;clip-on applications tightly coupled to the ZLE services; and a serverexecuting and monitoring transactions related to the businesstransactions, the server being operatively connected to the dynamiccentral repository so that the business transactions can be conductedacross the enterprise with reduced latencies.
 5. The ZLE framework ofclaim 4 enabling the enterprise to run as a ZLE.
 6. The ZLE framework ofclaim 4 being extensible and available and enabling the enterprise tobecome extensible and available.
 7. The ZLE framework of claim 4defining a multilevel architecture with a hub, wherein the dynamiccentral repository and ZLE services reside on top of the server at thehub, and the enterprise applications are loosely coupled to the hub andcommunicating therewith via adapters.
 8. A system in an informationtechnology infrastructure of an enterprise that conducts businesstransactions in relation to which the enterprise experiences a pluralityof events occurring in sites across the enterprise, the system forenabling the enterprise to run as a zero latency enterprise (ZLE), thesystem comprising: enterprise applications installed in relation torespective sites across the enterprise; a ZLE core configured withenterprise applications integration and propagation of informationrelated to the events across the enterprise, dynamic central repositoryconfigured with dynamic real-time data warehouse and database managementaccess to which being correspondingly available to the enterpriseapplications and through which a real time coherent view of theinformation is available to the enterprise applications from across theenterprise, ZLE services coupled with the dynamic central repository andoperatively connected with the enterprise applications, transactionprocessing and monitoring relative to the dynamic central repository sothat the business transactions can be conducted across the enterprisewith reduced latencies; clip-on applications tightly coupled to the ZLEcore; and data mining and analysis technology operatively connected tothe dynamic central repository.
 9. The system of claim 8 enabling theenterprise to run as a ZLE.
 10. The system of claim 8 being extensibleand available and enabling the enterprise to become extensible andavailable.
 11. The system of claim 8 having a multilevel architecture inwhich the enterprise applications and loosely coupled to the ZLE corevia corresponding adapters.
 12. The system of claim 8, wherein theinformation is associated with indicia of the events, the system beingconfigured for capturing and processing the indicia in real time. 13.The system of claim 8, wherein the system is configured for real-timerecognition of the events, and wherein the system is configured forgathering the information related with the events from the sites acrossthe enterprise.
 14. The system of claim 8, wherein the informationincludes real-time event data, business transaction state data, andlookup data.
 15. The system of claim 8 in which the dynamic real-timedata warehouse and database management is implemented at the ZLE core inan operational data store (ODS) with a relational data base managementsystem (RDBMS).
 16. The system of claim 15 in which the ODS with theRDBMS is optimized for the enterprise application integration as well asreal-time loads, extractions, updates and queries.
 17. The system ofclaim 15 in which the information can be indexed by customeridentification rather than by time.
 18. The system of claim 8 in whichthe dynamic real-time data warehouse and database management isconfigured for dynamic data caching, historical data caching, messagestorage and state engine, and real-time data warehousing.
 19. The systemof claim 18, wherein the message storage is configured for use inpublish and subscribe operations.
 20. The system of claim 18, whereinthe state engine is configured for maintaining real-time synchronizationwith the business transactions, the state engine supporting workflowmanagement and allowing state tracking of ongoing business transactions.21. The system of claim 20, wherein the state tracking of ongoingbusiness transactions includes tracking of a value through productionand delivery by the enterprise, and wherein the system allows theenterprise to produce and deliver the value more efficiently.
 22. Thesystem of claim 18, wherein the real-time data warehousing provides datato data marts and to the data mining and analysis.
 23. The system ofclaim 8 wherein the dynamic real-time data warehouse and databasemanagement reduces data dependency between the enterprise applications.24. The system of claim 8 to which new enterprise application can beadded, wherein the dynamic real-time data warehouse and databasemanagement provides a historic account of events that can be used by thenewly added enterprise application.
 25. The system of claim 8 in whichthe transaction processing and monitoring at the ZLE core is implementedin a server environment that includes a server or a server cluster. 26.The system of claim 15, wherein the ODS with the RDBMS is cluster aware.27. The system of claim 25, wherein the server environment is configuredfor real-time transaction management.
 28. The system of claim 25,wherein the server environment is configured for fault tolerance,parallel processing, support of concurrent transaction processing andmonitoring of transactions flow through the system.
 29. The system ofclaim 25, wherein server environment provides an application serverenvironment as a common, standard-based framework for interfacing withthe enterprise applications, thereby proving transactional integrity.30. The system of claim 25, wherein the server environment provides ahigher level of system extensibility, system availability and dataintegrity.
 31. The system of claim 25, wherein the server environmentresides on a NonStop™ Hymalaya™ server cluster platform based on TuxedoCorba or Java technologies for optimized interoperability.
 32. Thesystem of claim 25, wherein the server environment resides on anAlphaServer™ server cluster platform running True64™ UNIX operatingsystem based on Tuxedo Corba or Java technologies for optimizedinteroperability.
 33. The system of claim 25 in which the ZLE servicesat the ZLE core reside on top of a parallel processing platform for thetransaction processing and monitoring of the server environment.
 34. Thesystem of claim 8 in which the ZLE services at the ZLE core include arules service, a workflow service, a message transformation service, aparallel message routing and parallel database insertion service, anevent capture service, and an extraction, transformation and loadservice.
 35. The system of claim 8, wherein there is synergy between theZLE services such that the ZLE services can operate as one.
 36. Thesystem of claim 34, wherein the dynamic real-time data warehouse anddatabase management is implemented in an operational data store (ODS)with a relational database management system (RDBMS), and wherein theparallel message routing and database insertion service provides contentbased routing and facilitates use of the ODS with the RDBMS as acentralized message store and queuing system for efficient publish andsubscribe message operations.
 37. The system of claim 34, wherein theparallel message routing and database insertion service is configuredfor routing via components of the ZLE core rather than moving messagesdirectly between the enterprise applications, the parallel messagerouting and database insertion service being further configured forloading large volumes of messages on the dynamic real-time datawarehouse and database management at the ZLE core.
 38. The system ofclaim 34, wherein the rules service is configured to apply a rule thatis most applicable and to create a corresponding answer, in real timerelative to the occurrence of an event, the application of the rulesbeing uniform across the enterprise.
 39. The system of claim 34 furtherincluding a user interface, wherein the rules service enables creationand modification of business rules via the user interface.
 40. Thesystem of claim 34 in which the rules service creates an enterprise-wideuniform rule-driven platform for flow of any business transactioninformation.
 41. The system of claim 34 further comprising aninference-based rules engine, wherein the clip-on applications includean interaction manager around which the inference-based rules engine iswrapped, the inference-based rules engine being configured to find, inreal time, a rule that is most appropriate regardless of the complexityof the rule or the size of rules set, the inference-based rules enginebeing further configured for non-sequential and non-iterativecapability.
 42. The system of claim 41 wherein the interaction managerincludes middleware configured for parallel execution and connectivityautomation rather than building point-to-point links between theenterprise applications.
 43. The system of claim 34, wherein the rulesservice is configured for aggregating rules by the dynamic centralrepository at the ZLE core.
 44. The system of claim 34, wherein thedynamic real-time data warehouse and database management is implementedat the ZLE core with a state engine, and wherein the workflow service isconfigured to leverage the state engine for managing the flow andprocessing of the business transactions via the system and to provide areal-time view of ongoing business transactions state from across theenterprise.
 45. The system of claim 34, wherein the messagetransformation service at the ZLE core is configured for mappingdifferences in message syntax, semantics and values in order toassimilate diverse data between disparate message sources anddestinations.
 46. The system of claim 34, wherein the extraction,transformation and load service at the ZLE core is configured for bulkdata handling capability.
 47. The system of claim 34, wherein the eventcapture service is configured for capturing events from across theenterprise in real time.
 48. The system of claim 8 in which the ZLE coreis a virtual hub for the clip-on applications that are served by its ZLEservices.
 49. The system of claim 8, wherein the business transactionsare associated with enterprise business wherein the clip-on applicationsare configured for supplementing the ZLE services in providing abusiness-level functionality that leverages the ZLE core and customizesit for the enterprise business.
 50. The system of claim 34, wherein theclip-on applications are configured for providing real time frauddetection that uses the rules service at the ZLE core.
 51. The system ofclaim 8, wherein the clip-on applications include an interactionmanager, a narrowcaster, a campaign manager and a customer data manager.52. The system of claim 34, wherein the dynamic real-time data warehouseand database management at the ZLE core is implemented in an operationaldata store (ODS) with a relational database management system (RDBMS),and wherein the data mining and analysis is configured for retrievingbulk data from the ODS and leveraging the bulk data for a rule-basedanalysis and enterprise intelligence, the data mining and analysis beingcapable of creating models that can be delivered to the ZLE core and ODSand, as feedback, to any of the ZLE services or clip-on applications.53. The system of claim 8 further comprising a docking capability fordocking additional enterprise applications.
 54. The system of claim 8further comprising adapters through which the enterprise applications,being loosely coupled and logically connected to the ZLE core, caninterface with each other via the ZLE core.
 55. The system of claim 54,wherein each of the adapters is configured for interfaced solutions orintegrated solutions.
 56. The system of claim 8 configured to enableintegration, in real time, of enterprise-wide information, enterpriseapplications, business transactions and values.
 57. A system in aninformation technology infrastructure of an enterprise that conductsbusiness transactions in relation to which the enterprise experiences aplurality of events occurring in sites across the enterprise, the systemfor enabling the enterprise to run as a zero latency enterprise (ZLE),the system comprising: means for instantiating enterprise applicationsinstalled in relation to respective sites across the enterprise; a ZLEcore configured with means for instantiating enterprise applicationsintegration and propagation of information related to the events acrossthe enterprise, means for central dynamic real-time warehousing anddatabase management access to which being correspondingly available tothe enterprise applications and through which a real time coherent viewof the information is available to the enterprise applications fromacross the enterprise, means for instantiating ZLE services coupled withthe means for central dynamic real-time warehousing and databasemanagement and operatively connected with the enterprise applications,means for transaction processing and monitoring relative to the centraldynamic real-time warehousing and database management so that thebusiness transactions can be conducted across the enterprise withreduced latencies; means for instantiating clip-on applications whichare tightly coupled to the ZLE core; means for data mining and analysisthat is operatively connected to the means for dynamic centralwarehousing; and means for feeding back to the ZLE services results ofthe data mining and analysis and of data queries.
 58. A method forreducing latencies of business transactions conducted by an enterprisein an information technology (IT) infrastructure of the enterprise inrelation to which the enterprise t5 experiences a plurality of eventsoccurring at sites across the enterprise, the reduced latencies forenabling the enterprise to run as a zero latency enterprise (ZLE), themethod comprising: instantiating enterprise applications installed inrelation to respective sites across the enterprise; at a ZLE core withinthe IT infrastructure instantiating enterprise applications integrationand propagation of information related to the events across theenterprise, creating dynamic central repository configured with centraldynamic real-time warehousing and database management access to whichbeing correspondingly available to the enterprise applications andthrough which a real time coherent view of the information is availableto the enterprise applications from across the enterprise, instantiatingZLE services that are coupled with the dynamic central repository andare operatively connected with the enterprise applications, creatingtransaction processing and monitoring relative to the dynamic centralrepository so that the business transactions can be conducted across theenterprise with reduced latencies; instantiating clip-on applicationswhich are tightly coupled to the ZLE core; and instantiating data miningand analysis that is operatively connected to the dynamic centralrepository and providing feedback to the ZLE services.
 59. The ZLEframework of claim 4 being used as an integrated uniform multi-channelcustomer relationship manager.
 60. The ZLE framework of claim 4 beingused as an integrated internal business operation optimization andenterprise-wide view mechanism.
 61. The ZLE framework of claim 4 beingused as an integrated supply chian management and optimizationmechanism.
 62. The ZLE framework of claim 4 being used as a dashboardfor viewing, in real-time, a global status of any information relevantto the enterprise business.